chore: scaffold the repo and migrate the web app onto published npm#2
Merged
Conversation
Relocate the toolkit web app into its own repository, unchanged, with the /inspector route now consuming the published @ocpp-debugkit/toolkit npm package (^0.3.1) instead of a workspace dependency. - Next.js 16 / App Router / Tailwind v4 / strict TypeScript scaffold - Migrated landing, layout, inspector, and all docs pages as-is - Ported Playwright config + landing/inspector/replay specs - FOSS foundation: README, LICENSE, NOTICE, CONTRIBUTING, CODE_OF_CONDUCT, SECURITY, AGENTS, CURRENT_STATE, issue/PR templates, CI
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Stand up
ocpp-debugkit/websiteand relocate the toolkit web app into it —unchanged — with the
/inspectorroute running off the published@ocpp-debugkit/toolkitnpm package instead of a workspace dependency. This isthe "relocate, don't rewrite" step; the umbrella content rework (Studio coverage,
marketing refresh) lands next.
Changes
Playwright,
vercel.json.src/app/**(landing, layout, inspector, all docs pages) and thePlaywright specs moved as-is. No behavior change.
package.jsondepends on@ocpp-debugkit/toolkit@^0.3.1from npm. The inspector's import specifiers are unchanged — the published
package already exports
./core,./reporter,./scenarios,./replay.CODE_OF_CONDUCT, SECURITY (private-advisory reporting), AGENTS, CURRENT_STATE,
issue/PR templates, CI (build → typecheck → lint → e2e).
Verification
Local, against the published package (no workspace):
pnpm build— 17 routes build, including/inspector.pnpm typecheck— clean.pnpm lint— 0 errors (1 pre-existingexhaustive-depswarning carried oververbatim from the source; left untouched to preserve behavior).
pnpm test:e2e— 16 passed. The inspector + replay specs are the migrationsmoke test: they load a sample scenario and assert the timeline, failures, and
replay controls all render off the npm-backed toolkit.
Notes for reviewer
refresh + Studio coverage is the follow-up PR.
Closes #1